Skip to content

chore: add npm bugs metadata to all published packages#1200

Open
XananasX7 wants to merge 1 commit into
TanStack:mainfrom
XananasX7:fix/add-npm-bugs-metadata
Open

chore: add npm bugs metadata to all published packages#1200
XananasX7 wants to merge 1 commit into
TanStack:mainfrom
XananasX7:fix/add-npm-bugs-metadata

Conversation

@XananasX7

@XananasX7 XananasX7 commented Jun 15, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown

Problem

All @tanstack/virtual packages are missing the bugs field in their package.json files.

npm view @tanstack/react-virtual bugs    # empty
npm view @tanstack/virtual-core bugs    # empty
# etc.

Fix

Add bugs.url pointing to the GitHub issue tracker in all published packages. Metadata-only change — no runtime behaviour is affected.

Summary by CodeRabbit

Chores

  • Enhanced issue reporting workflow by adding official bug tracking URLs to package metadata across all virtualization framework libraries. This provides developers with streamlined, direct access to the project's issue tracker for bug reporting.
  • Improved package configuration consistency by correcting JSON structure and formatting across package manifest files.

@XananasX7
chore: add npm bugs metadata to all published packages
b449d3f 
All @tanstack/virtual and @tanstack/virtual-core packages are missing
the bugs field in package.json. Add bugs.url pointing to the GitHub
issue tracker across all packages.
@XananasX7 XananasX7 mentioned this pull request Jun 15, 2026
Open
@coderabbitai

coderabbitai Bot commented Jun 15, 2026 •
edited
Loading

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 411c9655-ad37-405c-abab-34e84ca9e4b9

📥 Commits

Reviewing files that changed from the base of the PR and between 932c358 and b449d3f.

📒 Files selected for processing (7)
  • packages/angular-virtual/package.json
  • packages/lit-virtual/package.json
  • packages/react-virtual/package.json
  • packages/solid-virtual/package.json
  • packages/svelte-virtual/package.json
  • packages/virtual-core/package.json
  • packages/vue-virtual/package.json
📝 Walkthrough

Walkthrough

All seven package.json files in the monorepo (virtual-core, angular-virtual, lit-virtual, react-virtual, solid-virtual, svelte-virtual, vue-virtual) receive a new top-level bugs field containing the GitHub issues URL. Two files (react-virtual, vue-virtual) also add a missing trailing comma on the peerDependencies closing brace.

Changes

Bugs URL metadata across all packages

Layer / File(s) Summary
Add bugs.url to all package manifests
packages/virtual-core/package.json, packages/angular-virtual/package.json, packages/lit-virtual/package.json, packages/react-virtual/package.json, packages/solid-virtual/package.json, packages/svelte-virtual/package.json, packages/vue-virtual/package.json		 Adds a bugs object with a GitHub issues URL to every package manifest. react-virtual and vue-virtual additionally fix a missing trailing comma on the peerDependencies closing brace to keep the JSON valid.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 Hop, hop, a URL appears,
In every package.json it cheers!
When bugs come knocking, now we know
Exactly where the issues go.
A tidy comma fixed the rest—
This little rabbit passed the test! 🎉

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The description adequately explains the problem and fix, but is missing required checklist items and release impact declaration from the template. Complete the checklist items and explicitly state whether this change requires a changeset or if it is dev-only.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: adding npm bugs metadata to all published packages.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@XananasX7